Methods of processing data corresponding to a device that corresponds to a gas, water, or electric grid, and related devices and computer program products

ABSTRACT

Methods of operating a communication node are provided. A method of operating a communication node may include receiving data from an electric grid device via a network interface. The method may include processing the data from the electric grid device at the communication node. Moreover, the method may include transmitting a filtered portion of the data to an electric utility head end system, after processing the data at the communication node. In some embodiments, a method of operating a communication node may include using a message broker controlled by a virtual machine in the communication node to provide a protocol to interface with a field message bus that includes a standards-based or open-source Application Programming Interface (API). Related communication nodes and computer program products are also described.

CLAIM OF PRIORITY

The present application claims the benefit of U.S. Provisional PatentApplication Ser. No. 61/886,496, filed Oct. 3, 2013, entitled Methods ofProcessing Data Corresponding to an Electric Grid Device, and RelatedCommunication Nodes and Computer Program Products, the disclosure ofwhich is hereby incorporated herein in its entirety by reference.

FIELD

The present disclosure relates to data that corresponds to a gas, water,or electric grid.

BACKGROUND

An electric grid may include various electric grid devices, which may beintelligent, interconnected equipment that deliver, monitor, measure,and/or control the flow of electricity in a power delivery system. Theelectric grid may also include a telecommunications infrastructure fortransporting and delivering information regarding the electric grid, aswell as analytics, architecture, and data-management tools formanaging/optimizing the electric grid. Moreover, a wide variety ofelectric grid customer-owned assets, which may consume, store, orproduce electricity, may be connected to the electric grid.

As an electric grid, and various interconnected customer-owned devicesand electric grid devices in the electric grid, become more complex, itmay be more difficult to meet electric utility customers' demandsregarding response times, costs, safety, and reliability. For example,an electric grid may reach diverse geographies, customers, and vendortechnologies. Accordingly, processing data and managing electric griddevices may be costly and time-consuming.

SUMMARY

It should be appreciated that this Summary is provided to introduce aselection of concepts in a simplified form, the concepts being furtherdescribed below in the Detailed Description. This Summary is notintended to identify key features or essential features of thisdisclosure, nor is it intended to limit the scope of the presentinventive concepts.

Various embodiments of the present inventive concepts include a methodof operating a communication node. The method may include receiving datafrom an electric grid device via a network interface. In someembodiments, the network interface may include a local area networkinterface or a wide area network interface. The method may includeprocessing the data from the electric grid device at the communicationnode. In some embodiments, processing the data may include readingApplication Layer data at the communication node. Moreover, the methodmay include transmitting a filtered portion of the data to a data centerincluding an electric utility head end system, after processing the dataat the communication node. In some embodiments, a computer programproduct including a non-transitory computer readable storage mediumincluding computer readable program code therein may be configured toperform the method.

According to various embodiments, the filtered portion of the datareceived from the electric grid device may include at least one electricgrid parameter, networking parameter, customer parameter, securityparameter, device identification parameter, or time-stamp parameter. Insome embodiments, the electric grid device parameter may be a voltage.Additionally or alternatively, it will be understood that operations ofprocessing the data may include determining a response decision, withrespect to the electric grid device or with respect to another electricgrid device regarding which the electric grid device provides the data.In some embodiments, the method may include transmitting the responsedecision to the electric utility head end system.

In various embodiments, the electric grid device may be a first electricgrid device, and the communication node may be a first communicationnode corresponding to the first electric grid device. Moreover, themethod may include transmitting the filtered portion of the data to asecond communication node corresponding to a second electric griddevice, via a field message bus. Additionally or alternatively, themethod may include receiving filtered data from a second communicationnode corresponding to a second electric grid device, via a field messagebus. In some embodiments, the first and second communication nodes maycorrespond to different first and second vendors, respectively.Additionally or alternatively, the first and second communication nodesmay correspond to different first and second hierarchical tiers,respectively, in a hierarchical arrangement of communication nodes.

A method of operating a communication node, according to variousembodiments, may include using a message broker controlled by a virtualmachine in the communication node to provide a protocol to interfacewith a field message bus including a standards-based or open-sourceApplication Programming Interface (API). Moreover, the method mayinclude transmitting or receiving data corresponding to an electric griddevice, via the field message bus. In some embodiments, a computerprogram product including a non-transitory computer readable storagemedium including computer readable program code therein may configuredto perform the method.

In various embodiments, the communication node may be a firstcommunication node, and the field message bus may interface with asecond communication node. Moreover, the first and second communicationnodes may be respective peer communication nodes having the fieldmessage bus therebetween. In some embodiments, the first and secondcommunication nodes may correspond to different first and secondvendors, respectively. Additionally or alternatively, the first andsecond communication nodes may correspond to different first and secondhierarchical tiers, respectively, in a hierarchical arrangement ofcommunication nodes.

According to various embodiments, the method may include using theprotocol of the message broker to interface with a translator unit thatis between a device protocol and the field message bus. Additionally oralternatively, the method may include using the protocol of the messagebroker to interface with a standards-based or open-source-API-basedapplication in the communication node. In some embodiments, the methodmay include using the protocol of the message broker to interface with aplurality of field message buses.

According to various embodiments, the virtual machine may operate usingan application processor or a partition of a central processing unit ofthe communication node. Additionally or alternatively, the method mayinclude isolating an application processing unit of the communicationnode from a central processing unit of the communication node, using thevirtual machine.

A communication node, according to various embodiments, may include anetwork interface configured to provide communications with a firstelectric grid device. The communication node may include a processorconfigured to control a virtual machine in the communication node.Moreover, the virtual machine may be configured to provide a messagebroker that is configured to interface with a field message bus and/oranother communication node corresponding to a second electric griddevice. In some embodiments, the first electric grid device may be anelectric utility meter, a transformer, a light, an electric grid controldevice, an electric grid protection device, a line sensor, a weathersensor, an Advanced Metering Infrastructure (AMI) device, an analog ordigital sensor connected to an electric utility asset, an electricgenerator, an electric turbine, an electric boiler, an electric vehicle,an intelligent switching device, a home appliance, a battery storagedevice, a capacitor device, a solar power device, a smart generationdevice, an emission monitoring device, or a voltage regulator.

In various embodiments, the network interface may include a local areanetwork interface configured to provide communications with the firstelectric grid device. In some embodiments, the local area networkinterface may be configured to provide communications with a pluralityof electric grid devices.

According to various embodiments, the network interface may beconfigured to receive data from the first electric grid device via thenetwork interface. Moreover, the virtual machine may be configured toprocess the data from the first electric grid device at thecommunication node, and the virtual machine may be configured to controltransmission of a filtered portion of the data to an electric utilityhead end system, after processing the data at the communication node. Insome embodiments, the filtered portion of the data received from thefirst electric grid device may include at least one electric grid deviceparameter (e.g., a voltage), networking parameter, customer parameter,security parameter, device identification parameter, or time-stampparameter.

In various embodiments, the virtual machine may be configured to processthe data from the first electric grid device by determining a responsedecision, with respect to the first electric grid device or with respectto a third electric grid device regarding which the first electric griddevice provides the data. In some embodiments, the virtual machine maybe configured to control transmission of the response decision to theelectric utility head end system. Moreover, in some embodiments, thevirtual machine may be configured to process the data from the firstelectric grid device by reading Application Layer data from the electricgrid device.

According to various embodiments, the communication node may be a firstcommunication node corresponding to the first electric grid device, andthe other communication node may be a second communication nodecorresponding to the second electric grid device. Moreover, the virtualmachine may be configured to control transmission of the filteredportion of the data to the second communication node corresponding tothe second electric grid device, via the field message bus. Additionallyor alternatively, the virtual machine may be configured to receivefiltered data from the second communication node corresponding to thesecond electric grid device, via the field message bus. In someembodiments, the electric utility head end system may be configured toprovide communications via a data center message bus, and the fieldmessage bus may be configured to provide communications independently ofthe data center message bus.

According to various embodiments, the field message bus may include astandards-based or open-source Application Programming Interface (API).Moreover, the message broker may be configured to provide a protocol tointerface with the field message bus that includes the standards-basedor open-source API, and the virtual machine may be configured totransmit or receive data corresponding to the second electric griddevice, via the field message bus. In some embodiments, thecommunication node may be a first communication node, the othercommunication node may be a second communication node configured tointerface with the field message bus, and the first and secondcommunication nodes may be respective peer communication nodes includingthe field message bus therebetween. Moreover, in some embodiments, thefirst and second communication nodes may correspond to different firstand second vendors, respectively.

In various embodiments, the protocol of the message broker may beconfigured to interface with a translator unit that is between a deviceprotocol and the field message bus. Additionally or alternatively, theprotocol of the message broker may be configured to interface with astandards-based or open-source-API-based application in thecommunication node. Moreover, the protocol of the message broker may beconfigured to interface with a plurality of field message buses.

According to various embodiments, the virtual machine may be configuredto operate using an application processor or a partition of a centralprocessing unit of the communication node. In some embodiments, thevirtual machine may be configured to isolate an application processingunit of the communication node from a central processing unit of thecommunication node.

A method of operating a first device corresponding to a gas, water, orelectric grid, according to various embodiments, may include receivingdata, via a network interface, from a second device corresponding to thegas, water, or electric grid. The method may include processing the datafrom the second device at the first device. Moreover, the method mayinclude transmitting a filtered portion of the data to a data centerincluding an utility head end system corresponding to the gas, water, orelectric grid, after processing the data at the first device. In someembodiments, a computer program product including a non-transitorycomputer readable storage medium that includes computer readable programcode therein may be configured to perform the method.

In various embodiments, the network interface may include a local areanetwork interface or a wide area network interface. Moreover, thefiltered portion of the data received from the second device may includeat least one electric grid parameter, water grid parameter, gas gridparameter, networking parameter, customer parameter, security parameter,device identification parameter, or time-stamp parameter. In someembodiments, processing the data may include determining a responsedecision at the first device, with respect to the data received from thesecond device. Moreover, the response decision may include a response toan event at the second device or at a third device corresponding to thegas, water, or electric grid.

According to various embodiments, the method may include transmittingthe response decision to the utility head end system. In someembodiments, the method may include transmitting the response decisionto a third device corresponding to the gas, water, or electric grid.Moreover, the first, second, and third devices may include first,second, and third electric grid devices, respectively, corresponding tothe electric grid, and transmitting the response decision may includetransmitting the response decision from the first electric grid deviceto the utility head end system and to the third electric grid device.Alternatively, the first and second devices may include first and secondelectric grid devices, respectively, corresponding to the electric grid,the third device may include a communication node corresponding to athird electric grid device that corresponds to the electric grid, andtransmitting the response decision may include transmitting the responsedecision from the first electric grid device to the utility head endsystem and to the communication node corresponding to the third electricgrid device. Alternatively, the first device may include a communicationnode corresponding to a first electric grid device that corresponds tothe electric grid, the second and third devices may include second andthird electric grid devices, respectively, corresponding to the electricgrid, and transmitting the response decision may include transmittingthe response decision from the communication node corresponding to thefirst electric grid device to the utility head end system and to thethird electric grid device.

In various embodiments, processing the data may include readingApplication Layer data at the first device. Moreover, the utility headend system may be configured to provide communications via a data centermessage bus, and the method may include transmitting the filteredportion of the data to a third device corresponding to the gas, water,or electric grid, via a field message bus that is configured to providecommunications independently of the data center message bus. In someembodiments, the first and second devices may correspond to differentfirst and second vendors, respectively. In some embodiments, the firstdevice may include an electric grid device, a water grid device, a gasgrid device, a telecommunications system device, a server, or a homeappliance.

A method of operating a first device corresponding to a gas, water, orelectric grid, according to various embodiments, may include using amessage broker and/or message client including an embedded protocol thatis standardized with respect to a field message bus that includes astandards-based or open-source Application Programming Interface (API),at the first device. The method may include transmitting or receivingdata corresponding to a second device corresponding to the gas, water,or electric grid, via the field message bus. Moreover, the first devicemay be spaced apart from a data center including an utility head endsystem, and the field message bus may be configured to providecommunications independently of a data center message bus of the utilityhead end system. In some embodiments, a computer program productincluding a non-transitory computer readable storage medium thatincludes computer readable program code therein may be configured toperform the method.

In various embodiments, the first and second devices may correspond todifferent first and second vendors, respectively. In some embodiments,the method may include using the embedded protocol of the message brokerand/or the message client to interface with a translator unit that isbetween a device protocol and the field message bus. In someembodiments, the method may include using the embedded protocol of themessage broker and/or the message client to interface with astandards-based or open-source-API-based application in the firstdevice. Moreover, in some embodiments, the method may include using theembedded protocol of the message broker and/or the message client tointerface with a plurality of field message buses.

A first device corresponding to a gas, water, or electric grid,according to various embodiments, may include a network interfaceconfigured to provide communications with a second device correspondingto the gas, water, or electric grid, via a field message bus including astandards-based or open-source Application Programming Interface (API).The first device may include a processor configured to control a messagebroker and/or message client in the first device, the message brokerand/or message client including an embedded protocol that isstandardized with respect to the field message bus. Moreover, the firstdevice may be spaced apart from a data center including an utility headend system, and the field message bus may be configured to providecommunications independently of a data center message bus of the utilityhead end system.

In various embodiments, the network interface may include a local areanetwork interface or a wide area network interface configured to providecommunications with the second device. The network interface may beconfigured to provide communications with a plurality of devicescorresponding to the gas, water, or electric grid.

According to various embodiments, the first device may include anelectric utility meter, a transformer, a light, an electric grid controldevice, an electric grid protection device, a line sensor, a weathersensor, an Advanced Metering Infrastructure (AMI) device, an analog ordigital sensor connected to an electric utility asset, an electricgenerator, an electric turbine, an electric boiler, an electric vehicle,an intelligent switching device, a home appliance, a battery storagedevice, a capacitor device, a solar power device, a smart generationdevice, an emission monitoring device, a water heater, a server, or avoltage regulator.

In various embodiments, the network interface may be configured toreceive data from the second device via the network interface. Theprocessor may be configured to process the data from the second deviceat the first device. Moreover, the processor may be configured tocontrol transmission of a filtered portion of the data to the utilityhead end system, after processing the data at the first device. In someembodiments, the filtered portion of the data received from the seconddevice may include at least one electric grid parameter, water gridparameter, gas grid parameter, networking parameter, customer parameter,security parameter, device identification parameter, or time-stampparameter.

According to various embodiments, the first and second devices maycorrespond to different first and second vendors, respectively. In someembodiments, the embedded protocol of the message broker and/or messageclient may be configured to interface with a translator unit that isbetween a device protocol and the field message bus. In someembodiments, the embedded protocol of the message broker and/or messageclient may be configured to interface with a plurality of field messagebuses.

A first device corresponding to a gas, water, or electric grid,according to various embodiments, may be provided. The first device mayinclude a network interface configured to provide communications with asecond device corresponding to the gas, water, or electric grid, via afield message bus including a standards-based or open-source ApplicationProgramming Interface (API). Moreover, the first device may include aprocessor configured to control a brokerless messaging protocol in thefirst device, and the brokerless messaging protocol may be an embeddedprotocol that is standardized with respect to the field message bus. Thefirst device may be spaced apart from a data center including an utilityhead end system. The field message bus may be configured to providecommunications independently of a data center message bus of the utilityhead end system. In some embodiments, the processor may be configured tocontrol the brokerless messaging protocol to communicate with a protocolof a message broker in a third device, via a local area network. In someembodiments, the processor may be configured to control the brokerlessmessaging protocol to communicate with the second device via the fieldmessage bus, and the processor may be configured to control a protocolof a message broker in the first device to communicate with a thirddevice via a local area network.

In various embodiments, the processor may be configured to control thebrokerless messaging protocol to contextualize data independently of(i.e., outside of) the data center. In some embodiments, the firstdevice further may include a memory that includes an enterprise-widesecurity application that is on every device in an enterprise that thefirst and second devices. In some embodiments, the processor may beconfigured to control communications via the field message bus accordingto an enterprise-wide semantic model (e.g., a common semantic model).Moreover, the processor may be configured to control a determination ofcapabilities of the second device, and the processor may be configuredto control incorporation (e.g., inclusion/input) of the capabilities ofthe second device into the enterprise-wide semantic model.

According to various embodiments, the processor may be configured toshare a portion of a processing capacity or a storage capacity of thefirst device with the second device. In some embodiments, the firstdevice may include reprogrammable hardware, and the processor may beconfigured to reprogram the reprogrammable hardware in response to acommand received (at the first device) via the field message bus.

It is noted that aspects of the present inventive concepts describedwith respect to one embodiment may be incorporated in a differentembodiment although not specifically described relative thereto. Thatis, all embodiments and/or features of any embodiment can be combined inany way and/or combination. Applicants reserve the right to change anyoriginally filed claim or file any new claim accordingly, including theright to be able to amend any originally filed claim to depend fromand/or incorporate any feature of any other claim although notoriginally claimed in that manner. These and other objects and/oraspects of the present inventive concepts are explained in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which form a part of the specification,illustrate various embodiments of the present inventive concepts. Thedrawings and description together serve to fully explain embodiments ofthe present inventive concepts.

FIG. 1A is a prior art schematic illustration of a data center messagebus at an electric utility data center.

FIG. 1B is a prior art schematic illustration of determining a response,at an electric utility data center, to an event regarding an electricgrid device.

FIG. 1C is a schematic illustration of a field message bus used bycommunication nodes corresponding to electric grid devices, according tovarious embodiments.

FIG. 1D is a schematic illustration of determining a response, at acommunication node, to an event regarding an electric grid device,according to various embodiments.

FIG. 1E is a block diagram of a communication node of FIGS. 1C and 1D,according to various embodiments.

FIG. 1F is a block diagram that illustrates details of an exampleprocessor and memory that may be used in accordance with variousembodiments.

FIGS. 2A-2F are flowcharts illustrating operations of a communicationnode of FIGS. 1C-1F, according to various embodiments.

FIGS. 3A-3F are flowcharts illustrating operations of a communicationnode of FIGS. 1C-1F, according to various embodiments.

FIGS. 4 and 5 are schematic illustrations of various networks linkingelectric grid devices, communication nodes, and electric utility datacenter head end systems, according to various embodiments.

FIGS. 6 and 7 illustrate block diagrams of field message bus datamodels, according to various embodiments.

FIG. 8 illustrates a schematic diagram of how a field message bus helpsconverge Information Technology (IT), telecommunications (Telecom)activities, and Operational Technology (OT), according to variousembodiments.

FIG. 9 illustrates a schematic diagram of additional details of theschematic diagram illustrated in FIG. 8, according to variousembodiments.

FIGS. 10A-10C are schematic illustrations of determining a response toan event regarding an electric grid device, according to variousembodiments.

FIGS. 11A-11D are flowcharts illustrating operations of a devicecorresponding to a gas, water, or electric grid, according to variousembodiments.

FIGS. 12A-12C are flowcharts illustrating operations of a devicecorresponding to a gas, water, or electric grid, according to variousembodiments.

FIG. 13 illustrates a data modeling and analytics framework, accordingto various embodiments.

DETAILED DESCRIPTION

Specific example embodiments of the present inventive concepts now willbe described with reference to the accompanying drawings. The presentinventive concepts may, however, be embodied in a variety of differentforms and should not be construed as limited to the embodiments setforth herein. Rather, these embodiments are provided so that thisdisclosure will be thorough and complete and will fully convey the scopeof the present inventive concepts to those skilled in the art. In thedrawings, like designations refer to like elements. It will beunderstood that when an element is referred to as being “connected,”“coupled,” or “responsive” to another element, it can be directlyconnected, coupled or responsive to the other element or interveningelements may be present. Furthermore, “connected,” “coupled,” or“responsive” as used herein may include wirelessly connected, coupled,or responsive.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinventive concepts. As used herein, the singular forms “a,” “an,” and“the” are intended to include the plural forms as well, unless expresslystated otherwise. It will be further understood that the terms“includes,” “comprises,” “including,” and/or “comprising,” when used inthis specification, specify the presence of stated features, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, steps, operations,elements, components, and/or groups thereof. As used herein, the term“and/or” includes any and all combinations of one or more of theassociated listed items. The symbol “/” is also used as a shorthandnotation for “and/or.”

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art to which these inventive concepts belong.It will be further understood that terms, such as those defined incommonly used dictionaries, should be interpreted as having a meaningthat is consistent with their meaning in the context of the relevant artand the present disclosure, and will not be interpreted in an idealizedor overly formal sense unless expressly so defined herein.

It will also be understood that although the terms “first” and “second”may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another element. Thus, a first element could be termeda second element, and similarly, a second element may be termed a firstelement without departing from the teachings of the present inventiveconcepts.

Example embodiments of the present inventive concepts may be embodied asnodes and methods. Accordingly, example embodiments of the presentinventive concepts may be embodied in hardware and/or in software(including firmware, resident software, micro-code, etc.). Furthermore,example embodiments of the present inventive concepts may take the formof a computer program product comprising a non-transitorycomputer-usable or computer-readable storage medium havingcomputer-usable or computer-readable program code embodied in the mediumfor use by or in connection with an instruction execution system. In thecontext of this document, a computer-usable or computer-readable mediummay be any medium that can contain, store, communicate, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device. More specificexamples (a nonexhaustive list) of the computer-readable medium wouldinclude the following: an electrical connection having one or morewires, a portable computer diskette, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, and a portable compact discread-only memory (CD-ROM). Note that the computer-usable orcomputer-readable medium could even be paper or another suitable mediumupon which the program is printed, as the program can be electronicallycaptured, via, for instance, optical scanning of the paper or othermedium, then compiled, interpreted, or otherwise processed in a suitablemanner, if necessary, and then stored in a computer memory.

Example embodiments of the present inventive concepts are describedherein with reference to flowchart and/or block diagram illustrations.It will be understood that each block of the flowchart and/or blockdiagram illustrations, and combinations of blocks in the flowchartand/or block diagram illustrations, may be implemented by computerprogram instructions and/or hardware operations. These computer programinstructions may be provided to a processor of a general purposecomputer, a special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means and/or circuits for implementingthe functions specified in the flowchart and/or block diagram block orblocks.

These computer program instructions may also be stored in a computerusable or computer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstructions that implement the functions specified in the flowchartand/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart and/or block diagram block or blocks.

Many solutions for managing electric grid devices and/or providing dataregarding electric grid devices are proprietary, are designed for use inonly one silo (e.g., are incapable of exchanging information with othersystems, vendors), and/or interoperate with other systems only afterexpensive and time-consuming integration efforts. For example, anelectric grid may reach diverse geographies, customers, and vendortechnologies that are not interoperable and therefore may not be capableof providing a necessary capability within a reasonable time period tomeet new or current needs. Various embodiments of the inventive conceptsdescribed herein, however, facilitate interoperability andinterchangeability between various operational technologies and augmentthese technologies by providing an interface for the efficient sharingand processing of data closer to the asset(s) (e.g., one or moreelectric grid devices), to rapidly, reliably, and safely executeoperational functions of the electric grid. As an example, it will beunderstood that interchangeability, as described herein, may refer tothe plug-and-play ability to add a new node (e.g., an end point) to anetwork/grid without having to set up the node using a head end system.

Specifically, a field message bus, on a communication node, canfacilitate interoperability and interchangeability between variousoperational technologies. The technologies may include, for example,Supervisory Control and Data Acquisition (SCADA), Energy ManagementSystem (EMS), Distribution Management System (DMS), Outage ManagementSystem (OMS), Meter Data Management (MDM), etc. Moreover, the fieldmessage bus may also augment such technologies by providing a commonpublish/subscription (pub/sub) logical interface for local data access,distributed intelligence, and peer-to-peer wireless communication on theelectric grid. Further value can be delivered by smart-grid activities,and the know-how can be shared with the utility industry to drivestandardization among the vendor community, resulting in greatereconomies of scale, improved economics of smart grid technologydeployment, enhanced asset performance, and a step closer towardconvergence between Information Technology (IT), Operational Technology(OT), and telecommunications activities (e.g., differenttelecommunications networks) of a grid.

In particular, communication nodes may provide a standards-based,modular communication platform, and may be configured to communicate viaa standards-based or open-source, broker-agnostic, peer-to-peer, anddistributed field message bus architecture. Moreover, the pub/submessaging interface provided by the field message bus may improve notonly the simplicity, integrity, and security of information exchangesbetween disparate assets in the field, but may also inherently filter asignificant amount of unused data overhead, and may reduce/eliminate theneed to backhaul all raw data to a central data center. These benefitscan translate into vast savings in the cost of operating IT systems andtelecommunications networks and can achieve further value by enablingdeployed control schemes that are not presently feasible withoutdistributed decision-making closer to the electric grid assets.

Additionally, the field message bus provides a messaging technology thatcan seamlessly integrate with existing communication nodes, withoutdisrupting any hardware and software functions presently on board. Thisnoninvasive implementation may employ a Virtual Machine (VM) tofunctionally isolate a communication node's application processingunit(s), where the message bus and its supporting logic may reside, froma Central Processing Unit (CPU), where existing network manageradministrative functions may continue to operate concurrently andsecurely backhaul all raw streaming SCADA data through each datacollector module, wired communication port, or radio modem. In parallel,the VM may listen to this existing pass-through device data and publish,by exception, copies of select shared data points to the field messagebus. Likewise, the VM may also allow Intelligent Electronic Devices(IEDs) connected to the communication node to subscribe to the fieldmessage bus for protection and control commands published by thedecoupled application processor(s). Loosely coupled to the VM may be awide variety of standards-based or open-source protocol adapters (e.g.,Modbus, Distributed Network Protocol (DNP), Simple Network ManagementProtocol (SNMP), IEC61850, etc.), object models (e.g., CommonInformation Model (CIM), and message brokers using standards-basedmessaging protocols (e.g., Message Queuing Telemetry Transport (MQTT),Advanced Messaging Queuing Protocol, AMQP, etc.) that collectively maycompress, decompress, encrypt, and translate data between disparatedevices, use-case application logic, and other communication nodes'field message buses.

It will be understood that the field message bus may have a wide numberof use-cases, including but not limited to Volt-VAR Optimization (VVO),self healing, Distributed Energy Resource Management System (DERMS),microgrid management, Photovoltaic (PV) smoothing, transformermonitoring, battery storage management, etc. The field message bus maybe used with various messaging protocols, including but not limited toAMQP, MQTT, Data Distribution Service (DDS), Java Message Service(JMS)), etc. Moreover, the field message bus may be used with variousbrokers/clients, such as Red Hat, Mosquitto, Webmethods, MQ, Apache,VMWare, etc., on different Operating Systems (OSs) (e.g., GoogleAndroid, Microsoft Windows, Red Hat Enterprise Linux (RHEL), EmbeddedLinux (E-Linux), etc.). Also, the field message bus may be used withvarious wireless and wired communication mediums, such as WiFi, 3G, LongTerm Evolution (LTE), 900 MegaHertz (MHz) Industrial, Scientific andMedical (ISM), Low Voltage (LV) or Medium/Mid Voltage (MV) Power LineCommunication/Carrier (PLC), Point-to-Point Radios, Microwave, ethernet,fiber-optics, serial, etc.

Accordingly, where vendors provide local data access from their devicesand application logic software, support head-end adapters and clientapplications to a common logical interface, and provide communicationnode firmware support for implementing a field message bus, the fieldmessage bus may seamlessly integrate with existing communication nodesand may facilitate interoperability between various operationaltechnologies. For example, the field message bus may enableinteroperability and interchangeability at all grid devices connected toa local area network of any communication node and any upstream head endsystem, using any telecommunications backhaul. In particular, using avirtual machine along with a standards-based or open-source API and abus, as described herein, may enable modularity of hardware,telecommunications, and software, as well as picking the best-in-breedtechnology, without having to worry about the integration between thembecause they all have a common information medium to share data.Moreover, in an environment where Distributed Energy Resources (DERs)may be rapidly adopted and where microgrids may benefit from fasterresponse times and cost-effective integration with a wide variety ofequipment, the field message bus can improve response times, reducecosts, improve safety, and improve reliability.

Referring now to FIG. 1A, a prior art schematic illustration is providedof a data center message bus 120 at an electric utility data center 130(e.g., a central office of an electric utility). The data center messagebus 120 connects head end systems H₁-H₃, which are each connected to oneor more electric grid devices E via respective communication networks.For example, electric grid device E₁ communicates with head end systemH₁ via a private carrier network 111, electric grid device E₂communicates with head end system H₂ via a proprietary network 112, andelectric grid devices E₃ and E₄ communicate with head end system H₃ viaa 3G/LTE network 114. Moreover, the electric grid devices E₃ and E₄communicate with each other via a 900 MHz ISM network 113. The electricgrid devices E₁-E₄ are each an element of an electric grid 100.

The electric grid devices E₁, E₂, and E₃ and E₄ correspond to (e.g.,belong to) different respective vendors V₁-V₃, which may be differenthardware/software manufacturers. Moreover, communications via thecommunication networks 111-114, regarding the electric grid devicesE₁-E₄, are not shared/understood between the vendors V₁-V₃ until afterreaching the data center message bus 120. Sharing data between theelectric grid devices E₁-E₄ may therefore be slow and inefficient.

Referring now to FIG. 1B, a prior art schematic illustration is providedof determining a response 192, at an electric utility data center 130,to an event 190 regarding an electric grid device E₃. For example, theevent 190 may be a rapid swing in production. In response to the event190 at the electric grid device E₃, data 191 regarding the electric griddevice E₃ is transmitted to the electric utility data center 130 via atleast one communication network 115 (e.g., a cellular network).Moreover, the electric grid device E₃ may be a street light, a loadbank, or a DER, such as a battery or a PV inverter, and may transmit thedata 191 to the communication network 115 via an electric grid deviceE₄, such as a distribution line sensor or a transformer monitoringdevice (e.g., a metrology chipset embedded inside a node). Thecommunication network 115 may include one or more wireless or wiredcommunication networks, such as the types of communication networks111-114 illustrated in FIG. 1A.

The electric utility data center 130 determines a response 192 to theevent 190, and then transmits the response 192 to one or more of theelectric grid devices E₁-E₅. In particular, the electric utility datacenter 130 includes at least one head end system H (e.g., one or more ofthe head end systems H₁-H₃ illustrated in FIG. 1A), and determines theresponse 192 after receiving the data 191 at the head end system H(e.g., a distribution line sensor head end or a meter head end). Inaddition to determining the response 192, the electric utility datacenter 130 updates (e.g., using a DMS therein) a model of the electricgrid 100 responsive to receiving the data 191. FIG. 1B's centralizedapproach of determining the response 192 at the electric utility datacenter 130, however, is a slow and inefficient way to respond to theevent 190.

Referring now to FIG. 1C, a schematic illustration is provided of afield message bus 140 used by communication nodes C₁ and C₂corresponding to electric grid devices E₁, E₂ and E₃, E₄, respectively,according to various embodiments. In particular, the communication nodesC₁ and C₂ may communicate data regarding the electric grid devices E₁-E₄before, or independently of, communicating data to the data centermessage bus 120 at the electric utility data center 130. Specifically,the field message bus 140 allows the communication nodes C₁ and C₂ toread/understand data that otherwise could only be read by a head endsystem H at an electric utility data center 130. For example, the fieldmessage bus 140 may host data (e.g., as a virtual host), andcommunication nodes C may process the data.

The communication nodes C₁ and C₂ may communicate with the electricutility data center 130 via the communication network 115. Thecommunication network 115 may include one or more wireless or wiredcommunication networks, such as fiber, Ethernet, or WiFi networks, orone or more of the types of communication networks 111-114 illustratedin FIG. 1A.

Referring now to FIG. 1D, a schematic illustration is provided ofdetermining a response 193/194, at a communication node C₁, to an event190 regarding an electric grid device E₃, according to variousembodiments. In contrast with determining a centralized response 192 atthe electric utility data center 130, as illustrated in FIG. 1B, thedistributed-decision-making approach illustrated in FIG. 1D ofdetermining the response 193/194 at the communication node C₁ maysignificantly improve decision/response times, reduce outage times, andreduce system operating costs. For example, the centralized response 192illustrated in FIG. 1B may take longer than fifteen minutes, whereas thedistributed response 193/194 illustrated in FIG. 1D may take less thanone second. Moreover, it will be understood that a distributed approach,as described herein, may refer to a multi-tier, connected network inwhich an application may be at one level/tier of the network and inputsmay be local to an electric grid device E at a different level/tier. Inother words, hardware, software, and telecommunications can be at anylevel/tier of the network. Moreover, various embodiments describedherein may provide interoperability and interchangeability of hardwareand software with Virtual LAN (VLAN) routers connected to a higher tiernode's message bus.

The communication node C₁ may transmit the response 193/194 to both theelectric utility data center 130 and one or more of the electric griddevices E₁-E₅ (e.g., via the field message bus 140 and the communicationnode C₂). In other words, the response 193 may include the samecontent/data as the response 194, but may have a different destination.Accordingly, it will be understood that a network interface of thecommunication node C₁ may be capable of multi-cast communications (e.g.,sending a transmission to both the communication node C₂ and the headend system H and/or to multiple communication nodes C) or peer-to-peercommunications. Moreover, a DMS of the electric utility data center 130may update a model of the electric grid 100 responsive to receiving theresponse 194. As the distributed-decision-making approach in FIG. 1Doccurs closer to the electric grid devices E₁-E₅ and reduces the burdenon the electric utility data center 130, it may significantly improvedecision/response times, reduce outage times, and reduce systemoperating costs.

Referring now to FIG. 1E, a block diagram is provided of a communicationnode C, according to various embodiments. The communication node C maybe one of the communication nodes C₁ and C₂ of FIGS. 1C and 1D, and mayinclude a processor 150 (including a core processor 151 and one or moreapplication processors 152), a network interface 160, and a memory 170.The network interface 160 is configured to provide a communicationsinterface with a field area network (which includes one or more fieldmessage buses), one or more local area networks, and/or one or more widearea networks (which may communicate with OT systems and/or othercommunication nodes C). For example, the network interface 160 may beconfigured to provide communications with an electric grid device Eand/or a field message bus 140. The network interface 160 may be forwired and/or wireless communications. Moreover, the processor 150 may beconfigured to control a virtual machine in the communication node C,where the virtual machine may be configured to provide a message brokerthat is configured to interface with the field message bus 140 and/oranother communication node C.

The processor 150 of the communication node C may be coupled to thenetwork interface 160. The processor 150 may be configured tocommunicate with electric grid devices E, other communication nodes C,and/or the electric utility data center 130 via the network interface160. For example, the network interface 160 may include one or morewireless interfaces 161 (e.g., 3G/LTE, other cellular, WiFi, GlobalPositioning System (GPS) interfaces, etc.) and one or more physicalinterfaces 162 (e.g., Ethernet, serial, Universal Serial Bus (USB)interfaces, etc.). Moreover, the network interface 160 may optionallyinclude one or more PLC interfaces 163 (e.g., Low Voltage (LV) or MVPLC). Additionally, the wireless interface(s) 161 may optionally include900 MHz radio.

Referring still to FIG. 1E, the memory 170 may be coupled to theprocessor 150, and may include a core memory 171 and an applicationmemory 172. The memory 170 may also store instructions/algorithms usedby the processor 150. The application memory 172 may store third-partyapplications, such as security/analytics applications. It will beunderstood that the capability to add various third-party applicationsto the application memory 172 can provide flexibility to thecommunication node C.

Moreover, the communication node C may optionally include a metrologychip that can obtain voltage/current data every second. Accordingly,such voltage/current data can be processed locally in the communicationnode C, which may be significantly faster than backhauling the datathrough a head end system H.

The communication node C may include core hardware components such as apower supply, 20 MHz or higher speed processor(s), and 1 Megabyte (MB)or more of RAM. The communication node C may also have a memory storagesuch as 1 MB or more of storage (e.g., Secure Digital (SD),MultiMediaCard (MMC), other Flash, etc.). Such modest core hardwarecomponents (in contrast with those of servers, super computers, etc.)demonstrate the considerable capabilities of a distributed intelligencesmart grid system to solve complex optimization problems. In otherwords, because the operations/computing described herein can bedistributed and shared across multiple processors and devices, the corehardware components may be modest. For example, in some embodiments,communication node C functionality may be provided by a virtual machineon any end device (rather than just a separate router box withtelecommunications).

The communication node C may include core applications, such asCPU/memory/OS management applications, port/device drivers,router/Internet Protocol (IP) services, network management services,basic protocol support, SCADA, custom API/applications, and devicesecurity services. Moreover, the communication node C may includevirtual applications, such as a virtual machine (e.g., a Java VirtualMachine), message bus(es), message broker(s), protocol adapters,mini-SCADA, open-standards API, and third-party applications (e.g.,security/analytics applications). The core applications may use suchsoftware as C++/Linux, and the virtual applications may use suchsoftware as Java/Linux. Additionally, the virtual applications may usethe application memory 172 and the application processor(s) 152.

Because the communication node C of FIG. 1E is interoperable with othercommunication nodes C and includes a modular hardware/software platform,the use of the communication nodes C allows a smart electric grid (e.g.,the grid 100) to be deployed gradually as economics and technologyallow. For example, a communication node C can be added when a meter isadded to the grid 100, or when a street light is added to the grid 100.

Referring now to FIG. 1F, a block diagram is provided that illustratesdetails of an example processor 150 and memory 170 of a communicationnode C that may be used in accordance with various embodiments. Theprocessor 150 communicates with the memory 170 via an address/data bus180. The processor 150 may be, for example, a commercially available orcustom microprocessor. Moreover, it will be understood that theprocessor may include multiple processors. The memory 170 isrepresentative of the overall hierarchy of memory devices containing thesoftware and data used to implement various functions of a communicationnode C as described herein. The memory 170 may include, but is notlimited to, the following types of devices: cache, ROM, PROM, EPROM,EEPROM, flash, Static RAM (SRAM), and Dynamic RAM (DRAM).

As shown in FIG. 1F, the memory 170 may hold various categories ofsoftware and data, such as an operating system 173. The operating system173 controls operations of a communication node C. In particular, theoperating system 173 may manage the resources of the communication nodeC and may coordinate execution of various programs by the processor 150.

Referring again to FIGS. 1C and 1D, an electric grid device E may be,for example, an electric utility meter, a transformer, a light (e.g., astreet light), an electric grid control device, an electric gridprotection device, a line sensor, a weather sensor, an Advanced MeteringInfrastructure (AMI) device, an analog or digital sensor connected to anelectric utility asset, an electric generator, an electric turbine, anelectric boiler, an electric vehicle, a home appliance, a batterystorage device, a capacitor device, a solar power device, a smartgeneration device, an intelligent switching device, an emissionmonitoring device, or a voltage regulator. It will be understood that anelectric grid device E described herein shall refer to any one of theelectric grid devices E₁-E₅ described herein. Moreover, it will beunderstood that more than five electric grid devices E may be includedin an electric grid 100. For example, dozens, hundreds, thousands, ormore electric grid devices E may be included in the electric grid 100.

Similarly, a communication node C shall refer to any one of thecommunication nodes C₁ and C₂ described herein, and dozens, hundreds,thousands, or more communication nodes C may be included. In particular,it will be understood that a communication node C may communicate with aplurality of other communication nodes C via one or more field messagebuses described herein. Additionally, a head end system H shall refer toany one of the head end systems H₁-H₃ described herein, and dozens,hundreds, thousands, or more head end systems H may be included.Furthermore, a vendor V shall refer to any one of the vendors V₁-V₃described herein, and dozens, hundreds, thousands, or more vendors V maybe included.

FIGS. 2A-2F are flowcharts illustrating operations of a communicationnode C of FIGS. 1C-1F, according to various embodiments. Referring nowto FIG. 2A, operations of the communication node C may include receivingdata (e.g., the data 191) from an electric grid device E via a networkinterface 160 (Block 201). In some embodiments, the network interface160 may include a local area network interface, such as a WiFi,Ethernet, USB, or serial interface. The operations may also includeprocessing the data from the electric grid device E at the communicationnode C (Block 202). Moreover, the operations may include transmitting afiltered portion of the data to an electric utility head end system H,after processing the data at the communication node C (Block 203).Additionally or alternatively, the operations may include processing thedata from the electric grid device E at an upstream operational head endsystem H or another communication node C. Furthermore, it will beunderstood that operations of transmitting the filtered portion of thedata may additionally or alternatively include transmitting atranslated, compressed, and/or encrypted portion of the data to anothercommunication node C. Similarly, it will be understood that thecommunication node C may receive filtered, translated, compressed,and/or encrypted data from another communication node C. Moreover, itwill be understood that a virtual machine at the communication node Cmay be configured to decrypt encrypted filtered data (and/or encryptedraw data) received from another communication node C via the fieldmessage bus 140.

Referring now to FIG. 2B, operations of processing the data may includedetermining, at the communication node C, a response decision (e.g., aresponse 193/194) with respect to the electric grid device E thatprovides data 191 or with respect to another electric grid device E(Block 202B). For example, it will be understood that the responsedecision may provide a decision that can be used/implemented by anelectric grid device E₃ having an event 190 and/or by another electricgrid device E (such as an electric grid device E₅, or an electric griddevice E₄ that provides the data 191 regarding the event 190). Moreover,transmitting the filtered portion of the data may include transmittingthe response decision (and/or a status) to the electric utility head endsystem H (Block 203B).

Referring now to FIG. 2C, operations of receiving data may includereceiving Application Layer (e.g., Layer 7) data (Block 201C). Moreover,operations of processing the data may include reading the ApplicationLayer data at the communication node C (Block 202C). Although theApplication Layer data is described herein as one example, the inventiveentity appreciates that operations of processing the data may includereading any logical layer data at the communication node C. For example,operations of processing the data may include reading data of any ofLayers 3-7 of the Open Systems Interconnection (OSI) model at thecommunication node C. As another example, operations of processing thedata may include reading Application Layer data of the TransmissionControl Protocol (TCP)/Internet Protocol (IP) model at the communicationnode C.

Referring now to FIG. 2D, operations of transmitting the filteredportion of the data received from the electric grid device E may includetransmitting at least one parameter in the data to the electric utilityhead end system H (Block 203D). It will be understood that theparticular electric grid device parameter(s) may depend on a specificuse case. For example, the parameter may include an electric gridparameter (e.g., a voltage or a current), a networking parameter (e.g.,a data transfer rate), a customer parameter (e.g., a willingness toparticipate in a program or service), a security parameter (e.g., akey), a device identification (ID) parameter, a time-stamp parameter, oran event notification (e.g., an alarm/alert).

Referring now to FIGS. 2E and 1C, the communication node C may be afirst communication node C₁ corresponding to a first electric griddevice E₁. Moreover, operations of the communication node C₁ may includetransmitting the filtered portion of the data to a second communicationnode C₂ corresponding to a second electric grid device E₄, via a fieldmessage bus 140 (Block 204).

Referring now to FIGS. 2F and 1C, the communication node C may be afirst communication node C₁ corresponding to a first electric griddevice E₁. Moreover, operations of the communication node C may includereceiving filtered, translated, compressed, and/or encrypted data from asecond communication node C₂ corresponding to a second electric griddevice E₄, via a field message bus 140 (Block 204F). For example,encrypted data may be communicated between communication nodes C, usinga field message bus 140 of a field area network. Accordingly, readingdata from the field message bus 140 may require a key to decrypt thedata. Referring still to FIGS. 2E and 2F, it will be understood that thefirst and second communication nodes C₁ and C₂ may correspond todifferent first and second vendors V, respectively. Accordingly, variousoperations described herein may be performed between devices/nodes ofdifferent vendors V. Additionally or alternatively, various operationsdescribed herein may be performed between devices/nodes of the samevendor V. For example, in some embodiments, the first and secondcommunication nodes C₁ and C₂ may correspond to the same vendor V.

FIGS. 3A-3F are flowcharts illustrating operations of a communicationnode C of FIGS. 1C-1F, according to various embodiments. Referring nowto FIG. 3A, operations of a communication node C may include using amessage broker that is controlled by a virtual machine in thecommunication node C to provide a protocol to interface with a fieldmessage bus 140 including a standards-based (e.g., a standard such asDNP, Microsoft Windows, etc.) or open-source Application ProgrammingInterface (API) (Block 301). In other words, the broker may be runningon the virtual machine inside the communication node C. Moreover, itwill be understood that application software of the communication node Cmay be written in any programming language supported by the agnosticmessage protocol used by the field message bus 140. Operations of thecommunication node C may also include transmitting or receiving data(e.g., the data 191) corresponding to an electric grid device E, via thefield message bus 140 (Block 302). Moreover, it will be understood thatthe operations illustrated in Block 302 of FIG. 3A may occur beforeand/or after the operations illustrated in Block 301.

In some embodiments, the virtual machine described with respect to Block301 of FIG. 3A may provide virtual telemetry that translates and sharesthe data 191. Without such virtual telemetry, the communication node Cwould send the data 191 to a head end system H, which would be a slowerand encrypted process. Accordingly, the virtual machine provides a wayto run the virtual telemetry and to interoperate between devices (e.g.,between different communication nodes C).

Referring now to FIG. 3B, the communication node C may be a firstcommunication node C₁ and the field message bus 140 may interface with asecond communication node C₂. Moreover, the first and secondcommunication nodes C₁ and C₂ may be respective peer communication nodesthat have the field message bus 140 therebetween. Accordingly,transmitting/receiving the data may include transmitting/receiving thedata corresponding to an electric grid device E to/from a peercommunication node via the field message bus 140 (Block 302B). The peercommunication nodes can communicate using the field message bus 140 evenif the peer communication nodes use different carriers (e.g., differentcellular carriers) because the field message bus 140 allows peer-to-peercommunications between carriers. In some embodiments, the first andsecond communication nodes C₁ and C₂ may correspond to different firstand second vendors V, respectively. Moreover, in some embodiments, thefirst and second communication nodes C₁ and C₂ may have a parent-childhierarchical arrangement, with the field message bus 140 between thefirst and second communication nodes C₁ and C₂. Additionally oralternatively, communications between the first and second communicationnodes C₁ and C₂ may use a plurality of communication methods. Forexample, the first communication node C₁ may send data to the secondcommunication node C₂ via a first communication method (e.g., one ofWiFi, cellular, PLC, etc.) and receive data from the secondcommunication node C₂ via a second communication method (e.g., adifferent one of WiFi, cellular, PLC, etc.).

Referring now to FIG. 3C, operations of the communication node C mayinclude using the protocol of the message broker (and/or a messageclient) to interface with a translator unit that is between a deviceprotocol and the field message bus 140 (Block 303). Moreover, it will beunderstood that the translator unit can be embedded in an electric griddevice E, a hardware interface of a communication node C, a centralprocessing unit, or a virtual machine. For example, an electric griddevice E having such a translator unit therein may therefore publishdata directly to the field message bus 140 (e.g., without using acommunication node C to publish data). It will also be understood thatthe device protocol (e.g., an end point protocol such as DNP, Modbus,SNMP, etc.) may be on an electric grid device E, the communication nodeC, and/or a head end system H.

Referring now to FIG. 3D, operations of the communication node C mayinclude using the protocol of the message broker to interface with astandards-based or open-source-API-based application in thecommunication node C (Block 303D).

Referring now to FIG. 3E, operations of the communication node C mayinclude using the protocol of the message broker to interface with aplurality of field message buses (Block 303E). In other words, themessage bus 140 may be one among a plurality of field message buses withwhich the communication node C may interface.

Referring now to FIG. 3F, operations of the communication node C mayinclude isolating an application processing unit (e.g., the applicationprocessor 152) of the communication node C from a central processingunit (e.g., the core processor 151) of the communication node C, usingthe virtual machine (Block 300). For example, the virtual machine mayprovide a virtual firewall between the application processor 152 and thecore processor 151, thus increasing security. As a result of the virtualfirewall, a particular communication node C may be quarantined from thefield message bus 140 without losing the entire network of communicationnodes C. For example, the field message bus 140 can compress and providesecure access to a field area network that does not exist for a publiccellular carrier or heterogeneous (public & private) network in which afirewall boundary only exists at a data center, and not at a substationor close to electric grid devices E. This distributed architecture,employing the field message bus 140, may extend the boundary of acorporate firewall to a substation that has a virtual LAN and it can dothis on any telecom WAN medium (e.g., including wired or wirelessmediums). Moreover, it will be understood that the operationsillustrated in Block 300 may be performed before and/or after theoperations illustrated in Block 301. Additionally or alternatively, itwill be understood that the virtual machine may operate using theapplication processor(s) 152 or a partition of the central processingunit of the communication node C.

FIGS. 4 and 5 are schematic illustrations of various networks linkingelectric grid devices E, communication nodes C, and electric utilitydata center head end systems H, according to various embodiments.Referring now, to FIG. 4, a Local Area Network (LAN) 410, a Field AreaNetwork (FAN) 420, a Wide Area Network (WAN) 430, and a corporateprivate network 440 are illustrated. For example, the LAN 410 mayinclude a first LAN for communications between electric grid devices E₁,E₂ and communication node C₁, and a second LAN for communicationsbetween electric grid devices E₃, E₄ and communication node C₂.

The FAN 420 may provide communications between the communication nodesC₁, C₂ via a field message bus 140. Moreover, multiple tiers ofcommunication nodes C may be provided. For example, the communicationnodes C₁, C₂ may be lowest-tier, edge communication nodes, whereas ahigher-tier communication node C₃ may be between the communication nodesC₁, C₂ and the corporate private network 440 (which is at the electricutility data center 130). As an example, the communication nodes C₁, C₂may be feeder communication nodes C, whereas the higher-tiercommunication node C₃ may be at a substation. In some embodiments, thehigher-tier communication node C₃ may manage the communication nodes C₁,C₂. Additionally or alternatively, another communication node C maymanage the higher-tier communication node C₃. In other words, the othercommunication node C may be in an even higher tier/level of hierarchythan the higher-tier communication node C₃ and may communicate with thehigher-tier communication node C₃ using peer-to-peer communications.Accordingly, referring still to FIG. 4, it will be understood thatadditional tiers may be provided, as well as that additional peercommunication nodes C may be included in the tiers.

The FAN 420 may provide communications between the, communication nodeC₁ and the higher-tier communication node C₃ via a field message bus421, and may provide communications between the communication node C₂and the higher-tier communication node C₃ via a field message bus 422.It will be understood that the block diagram of a communication node Cin FIG. 1E may apply to the higher-tier communication node C₃, as wellas the communication nodes C₁, C₂.

The WAN 430 may include a communication network 115 that communicateswith the corporate private network 440 via a network router that isbetween the communication network 115 and the head end systems H₁-H₃. Insome embodiments, the communication network 115 may be a Virtual PrivateNetwork (VPN). Moreover, it will be understood that one or moreadditional communication networks may be provided between thehigher-tier communication node C₃ and the electric utility data center130. For example, multiple vendors V may have respective communicationnetworks between the higher-tier communication node C₃ and aneven-higher-tier/level communication node C.

Referring now to FIG. 5, a communication network 511 may providecommunications between electric grid devices E₁, E₂ and communicationnode C₁, and a communication network 512 may provide communicationsbetween electric grid devices E₃, E₄ and communication node C₂. Thecommunication networks 511, 512 may each be local area networks. Forexample, the communication networks 511, 512 may be local area networksin the LAN 410 illustrated in FIG. 4. In some embodiments, a givencommunication node C may use a plurality of local area networks.Moreover, it will be understood that the communication networks 511, 512may use a message bus (e.g., a local field message bus) thatcontinuously pulls data from electric grid devices E and filters outdata that is not helpful/useful, thus increasing data processing speedin comparison with processing all data at an electric utility datacenter 130. In other words, a local message bus on a communication nodeC may perform real-time data streaming, and may do so while using thesame or different bus for global sharing between other communicationnodes that also are running a local message bus.

A field message bus 521 may provide communications between thecommunication node C₁ and communication network 513. Moreover, a fieldmessage bus 522 may provide communications between the communicationnode C₂ and the communication network 513. Also, field message buses532, 542 may provide communications between the communication network513 and a higher-tier communication node C₃ and a virtual gateway VGW atthe electric utility data center 130, respectively.

It will be understood that the communication network 513 may provide afield area network. Multiple vendors V may be connected to the samecommunication network 513, which may be a cellular network or a WiFinetwork, among other wireless or wired networks. Additionally, thecommunication network 513 may communicate Layer 7 data that can beread/understood by the communication nodes C.

The electric utility data center 130 may include a communication network514. For example, the communication network 514 at the electric utilitydata center 130 may include a corporate private network, such as thecorporate private network 440 illustrated in FIG. 4.

Referring now to FIG. 6, a block diagram of a field message bus datamodel is illustrated, according to various embodiments. The fieldmessage bus data model may include vendor V components, as well aselectric utility components and standards-based or open-sourcecomponents. For example, FIG. 6 illustrates that a vendor V's enddevice/OT system may include a meter, an IED, a sensor, an inverter,and/or a DMS. Moreover, a vendor V's application logic/IT system mayinclude VVO, Fault Detection, Isolation and Recovery/Restoration (FDIR),DER, security key management (Mgnt), and/or security.

Referring still to FIG. 6, an electric utility/system message bus mayinclude/provide a system-contextualized message. Moreover, the electricutility's local data access/adapters may include DNP, Modbus, orIEC61850 adapters, or C12, among others. Additionally, the field messagebus data model illustrated in FIG. 6 may include data compression andencryption.

The field message bus data model illustrated in FIG. 6 may also includevarious standards-based or open-source components. For example, astandards-based or open-source lightweight streaming broker may includeMQTT, AMQP, Data Distribution Service (DDS), and/or other messagingprotocols. An electric utility/field message bus may include translatedmessage syntax. A standards-based or open-source common model/Extract,Transform and Load (ETL) mapping may include/provide semanticabstraction. A standards-based or open-source agnostic publish/subscribeprotocol may include MQTT, DDS, AMQP, Datagram Transport Layer Security(DTLS), and/or other messaging protocols. Moreover, a standards-based oropen-source local data access/open API may be a standards-based protocolAPI.

Referring now to FIG. 7, another example of a block diagram of a fieldmessage bus data model is illustrated, according to various embodiments.The field message bus data model may include vendor V components, aswell as electric utility components and standards-based or open-sourcecomponents. For example, FIG. 7 illustrates that a vendor V's enddevice/OT system may include a PLC meter, Power Quality (PQ) Metrology,a 3G/4G router, a Capacitor (Cap) Bank Controller, an IP-enabled meter,a PV/battery inverter, a PI system, and/or a DMS. Moreover, a vendor V'sapplication logic/IT system may include an Undervoltage (UV)/Overvoltage(OV) Application (App), a transformer PQ alarm, security key management,and/or solar smoothing.

Referring still to FIG. 7, an electric utility's message bus mayinclude/provide a system translated and contextualized message.Moreover, the electric utility's local data access/adapters may includeDNP/Modbus/Simple Network Management Protocol (SNMP) protocol adapters,among others. Additionally, the field message bus data model illustratedin FIG. 7 may include data compression and encryption.

The field message bus data model illustrated in FIG. 7 may also includevarious standards-based or open-source components. For example, astandards-based or open-source lightweight streaming broker may includeMQTT, DDS, and/or AMQP. Moreover, a standards-based or open-source localdata access/open API may include a standards-based protocol API.

Referring now to FIG. 8, a schematic diagram illustrates how a fieldmessage bus helps converge IT, telecommunications (Telecom) activities,and OT, according to various embodiments. For example, IT may includeanalytics, such as one or more use-case applications (App(s)) in acommunication node C. The use-case application(s) may subscribe to datafrom an open API message bus (e.g., the field message bus 140) and/ormay publish data to the open API message bus.

Referring still to FIG. 8, OT may include translation components, suchas a head end, DNP, Modbus, and/or SNMP, and such translation componentsmay subscribe to data from the open API message bus and/or may publishdata to the open API message bus. Moreover, data between the translationcomponents and the open API message bus may be encrypted and/orcompressed, as illustrated in FIG. 8. Additionally, OT may include OTsystem or device components, such as a DMS, sandbox, Pi system, linesensor, intelligent switch, capacitor (Cap) bank, smart meter,battery/PV inverter(s), transformer, and/or telecommunication (Telco)router. For example, the DMS, sandbox, and Pi system may be located at adata center 130, and may communicate with the open API message bus via ahead end system H, whereas the line sensor, intelligent switch,capacitor (Cap) bank, smart meter, battery/PV inverter(s), transformer,and telecommunication (Telco) router may be electric grid devices E thatcommunicate with the open API message bus via one or more communicationnodes C. The communication node(s) C may communicate with the open APImessage bus using translation/messaging protocols such as thoseillustrated in FIG. 8.

Referring now to FIG. 9, a schematic diagram illustrates additionaldetails of the schematic diagram illustrated in FIG. 8, according tovarious embodiments. Moreover, FIG. 9 illustrates a comparison between aresponse time of a field message bus (less than about 500 milliseconds(ms)) and a corporate/enterprise bus (about 5 seconds). Additionally, itwill be understood that MSG BUSES 1-3 in FIG. 9 may be three differentfield message buses that provide pub/sub with analytics and/ortranslation. It will also be understood that the Comm Nodes illustratedin FIG. 9 may be communication nodes C, and that the OT system/devicecomponents illustrated in FIG. 9 as being communicatively coupled to thecommunication nodes C may be electric grid devices E. Furthermore, theXFMR illustrated in FIG. 9 may be a transformer, and the cellularnetworks may include LTE/Evolution-Data Optimized (EVDO) carrier andHigh Speed Packet Access (HSPA)/Global System for Mobile Communications(GSM) carrier networks.

Accordingly, in view of various embodiments described herein, a fieldmessage bus (e.g., a message bus 140 in the field rather than within anelectric utility data center 130) may enable interoperability betweenutility grid assets (e.g., electric grid devices E). For example, acommunication node C may be on/attached to an electric utility pole. Byusing the field message bus, sharing and processing of data will occurcloser to the utility grid assets (rather than at the electric utilitydata center 130). The field message bus and its supporting logic mayreside on the communication node C's application processing unit(s)(e.g., application processor(s) 152).

In particular, a field message bus may be a standards-based oropen-source Application Programming Interface (API), and a virtualmachine may be inside a communication node C and may isolate thecommunication node C's application processing unit(s) from a CentralProcessing Unit (CPU) (e.g., the core processor 151). Specifically, amessage broker may run on the virtual machine that is inside thecommunication node C.

The message broker may provide a protocol to interface between differentmessage buses and/or different communication nodes C. The messagebroker's protocol also may interface with an adapter (e.g., a translatorbetween a device protocol and a message bus) and applications (e.g.,applications based on a standards-based or open-source API).Accordingly, the message broker may enable interoperability betweenutility grid assets.

Also, instead of relying on an electric utility data center 130 toread/understand Application Layer (e.g., Layer 7) data, a communicationnode C in the field and using a field message bus can read/understandsuch Layer 7 data. Moreover, this field message bus technology mayseamlessly integrate with existing communication nodes C withoutdisrupting present hardware/software functions. For example, this fieldmessage bus technology may be agnostic to the communication medium(e.g., could be used with cellular communications or with PLCcommunications, etc.), agnostic to the hardware/vendor, agnostic to thesoftware language (e.g., could be used with Java, C++, Python, etc.),and agnostic to the Transport Layer.

Moreover, it will be understood that the functionality of acommunication node C described herein may be incorporated into anydevice with a processor, a memory, and a network interface. For example,the functionality of a communication node C described herein may beincorporated into a device corresponding to a utility grid (e.g., anelectric grid device E or a device corresponding to a gas or watergrid). Accordingly, although a communication node C may perform variousoperations described herein, it will be understood that one or moreother devices may perform the operations.

FIGS. 10A-10C are schematic illustrations of determining a response toan event regarding an electric grid device, according to variousembodiments. Referring now to FIG. 10A, a schematic illustration isprovided of determining a response 193/194, at an electric grid deviceE₄, to an event 190 regarding an electric grid device E₃, according tovarious embodiments. In contrast with determining a centralized response192 at the electric utility data center 130, as illustrated in FIG. 1B,the distributed-decision-making approach illustrated in FIG. 10A ofdetermining the response 193/194 at the electric grid device E₄ maysignificantly improve decision/response times, reduce outage times, andreduce system operating costs. For example, the centralized response 192illustrated in FIG. 1B may take longer than fifteen minutes, whereas thedistributed response 193/194 illustrated in FIG. 10A may take less thanone second. Moreover, it will be understood that a distributed approach,as described herein, may refer to a multi-tier, connected network inwhich an application may be at one level/tier of the network and inputsmay be local to an electric grid device E at a different level/tier. Inother words, hardware, software, and telecommunications can be at anylevel/tier of the network.

Moreover, various embodiments described herein may provideinteroperability and interchangeability of hardware and software withVirtual LAN (VLAN) routers connected to a higher tier node's messagebus.

Referring still to FIG. 10A, the electric grid device E₄ may transmitthe response 193/194 to both the electric utility data center 130 andone or more of the other electric grid devices E₁-E₃ and E₅ (e.g., viathe field message bus 140). In other words, the response 193 illustratedin FIG. 10A may include the same content/data as the response 194, butmay have a different destination. Moreover, a DMS of the electricutility data center 130 may update a model of the electric grid 100responsive to receiving the response 194. As thedistributed-decision-making approach in FIG. 10A occurs at one of theelectric grid devices E₁- E₅ and reduces the burden on the electricutility data center 130, it may significantly improve decision/responsetimes, reduce outage times, and reduce system operating costs.

Referring now to FIG. 10B, a schematic illustration is provided ofdetermining a response 193/194, at an electric grid device E₄, to anevent 190 regarding an electric grid device E₃, according to variousembodiments. In particular, FIG. 10B is a modification of FIG. 10A thatillustrates transmitting the response 193 to the electric grid device E₅via a communication node C corresponding to the electric grid device E₅.In other words, FIG. 10B illustrates that the electric grid device E₄may transmit the response 193/194 to both the electric utility datacenter 130 and one or more of the other electric grid devices E₁-E₃ andE₅ (e.g., via the field message bus 140 and the communication node C).

Referring now to FIG. 10C, a schematic illustration is provided ofdetermining a response 193/194, at a communication node C, to an event190 regarding an electric grid device E₃, according to variousembodiments. In particular, FIG. 10C is a modification of FIG. 10A thatillustrates determining the response 193/194 at the communication node C(instead of at the electric grid device E₄) and transmitting theresponse 193 from the communication node C to the electric grid deviceE₅ (without using an intervening communication node C between theelectric grid device E₅ and the transmitting communication node Cillustrated in FIG. 10C). In other words, FIG. 10C illustrates that thecommunication node C may directly transmit the response 193/194 to boththe electric utility data center 130 and one or more of the otherelectric grid devices E₁-E₃ and E₅ (e.g., via the field message bus140).

FIGS. 10A-10C provide examples illustrating that the functionality of acommunication node C described herein may be incorporated into anelectric grid device E that includes a processor, a memory, and anetwork interface. Moreover, it will be understood that althoughelectric grid devices E are illustrated in FIGS. 10A-10C, other devicescorresponding to a utility grid, such as devices corresponding to a gasgrid or a water grid, may perform the operations of a communication nodeC if the devices include a processor, a memory, and a network interface.

FIGS. 11A-11D are flowcharts illustrating operations of a first devicecorresponding to a gas, water, or electric grid, according to variousembodiments. For example, the operations may be performed in theelectric grid device E₄ illustrated in FIGS. 10A and 10B. Alternatively,the operations may be performed in the communication node C illustratedin FIG. 10C, or in a device corresponding to a water grid or a devicecorresponding to a gas grid.

Referring now to FIG. 11A, operations of the first device may includereceiving data (e.g., the data 191) from a second device (e.g., theelectric grid device E₃) via a network interface (Block 1101). It willbe understood that the second device may correspond to the same gas,water, or electric grid as the first device. Moreover, the networkinterface may include the functionality/components of the networkinterface 160 illustrated in FIG. 1E. For example, the network interfacemay include a local area network interface or a wide area networkinterface.

Referring still to FIG. 11A, the operations may also include processingthe data from the second device at the first device (Block 1102).Additionally, the operations may include transmitting a filtered portionof the data to a data center (e.g., the electric utility data center130) including an utility head end system H corresponding to the gas,water, or electric grid, after processing the data at the first device(Block 1103). Alternatively, in some embodiments, the operations ofBlock 1103 may include transmitting the filtered portion of the data toa third device in the field instead of to an utility head end system Hof a data center. In particular, in some embodiments, the functionalityof the head end system H may be incorporated into the third device thatis in the field, thus reducing the need for an utility head end system Hat a data center.

Referring now to FIG. 11B, operations of processing the data may includedetermining, at the first device, a response decision (e.g., a response193/194) with respect to the data received from the second device.(Block 1102B). For example, it will be understood that the responsedecision may provide a decision that can be used/implemented by thesecond device and/or by another device. As an example, the responsedecision may be a response to an event (e.g., an event 190) at thesecond device or at a third device corresponding to the gas, water, orelectric grid. Moreover, transmitting the filtered portion of the datamay include transmitting the response decision (and/or a status) to theelectric utility head end system H (Block 1103B).

Referring now to FIG. 11 C, operations of receiving data may includereceiving Application Layer (e.g., Layer 7) data (Block 1101C).Moreover, operations of processing the data may include reading theApplication Layer data at the first device (Block 1102C).

Referring now to FIG. 11D, operations of the first device may includetransmitting the filtered portion of the data and/or the responsedecision to a third device corresponding to the gas, water, or electricgrid, via a field message bus 140 (Block 1104).

Moreover, it will be understood that the filtered portion of the data,illustrated in Blocks 1103 and 1104, may include at least one electricgrid parameter, water grid parameter, gas grid parameter, networkingparameter, customer parameter, security parameter, device identificationparameter, or time-stamp parameter. In some embodiments, the firstdevice may be an electric grid device, a water grid device, a gas griddevice, a telecommunications system device, a server, or a homeappliance. Additionally or alternatively, the first and second devicesmay correspond to different first and second vendors, respectively.

In some embodiments, the utility head end system H may be configured toprovide communications via a data center message bus (e.g., the datacenter message bus 120). Moreover, operations of the first device mayinclude transmitting the filtered portion of the data to a third devicecorresponding to the gas, water, or electric grid, via a field messagebus 140 that is configured to provide communications independently ofthe data center message bus.

FIGS. 12A-12C are flowcharts illustrating operations of a first devicecorresponding to a gas, water, or electric grid, according to variousembodiments. For example, the operations may be performed in an electricgrid device E, a communication node C, or a device corresponding to awater grid or a gas grid. Moreover, it will be understood that theoperations in FIGS. 12A-12C may be performed without using a virtualmachine. Instead of using a virtual machine, the operations may includeusing a message broker and/or message client that includes an embeddedprotocol that is standardized with respect to a field message bus 140.In other words, virtualization (e.g., virtualization of transport,translation, and API to separate physical, logical, andnetwork/telecommunications layers) may occur using a message brokerand/or message client rather than a virtual machine.

Referring now to FIG. 12A, operations of the first device may includeusing a message broker and/or message client including an embeddedprotocol that is standardized with respect to a field message bus 140that includes a standards-based or open-source Application ProgrammingInterface (API), at the first device (Block 1201). Additionally,operations of the first device may include transmitting or receivingdata corresponding to a second device that corresponds to the gas,water, or electric grid, via the field message bus (Block 1202). Thefirst device may be spaced apart from a data center (e.g., an electricutility data center 130) that includes an utility head end system H.Moreover, the field message bus 140 may be configured to providecommunications independently of a data center message bus (e.g., thedata center message bus 120) of the utility head end system H.

Referring now to FIG. 12B, operations of the first device may includeusing the embedded protocol of the message broker and/or the messageclient to interface with a translator unit that is between a deviceprotocol and the field message bus 140 (Block 1203).

Referring now to FIG. 12C, operations of the first device may includeusing the embedded protocol of the message broker and/or the messageclient to interface with a standards-based or open-source-API-basedapplication in the first device (Block 1203C).

In some embodiments, operations of the first device indicated withrespect to FIGS. 12A-12C may include using the embedded protocol of themessage broker and/or the message client to interface with a pluralityof field message buses (e.g., one or more field message buses inaddition to the field message bus 140). Moreover, it will be understoodthat the first and second devices indicated with respect to FIGS.12A-12C may correspond to different first and second vendors,respectively.

In some embodiments, a first device indicated with respect to FIGS.11A-11D and 12A-12C may include a network interface that is configuredto provide communications with a second device, via a field message bus140 that includes a standards-based or open-source ApplicationProgramming Interface (API). For example, the network interface mayinclude the functionality/components of the network interface 160illustrated in FIG. 1E. As an example, the network interface may includea local area network interface or a wide area network interfaceconfigured to provide communications with the second device. In someembodiments, the network interface may be configured to providecommunications with a plurality of devices corresponding to the gas,water, or electric grid.

In some embodiments, the network interface may be configured to receivedata from the second device via the network interface. Moreover, theprocessor may be configured to process the data from the second deviceat the first device, and to control transmission of a filtered portionof the data to the utility head end system H after processing the dataat the first device. The filtered portion of the data received from thesecond device may include, for example, at least one electric gridparameter, water grid parameter, gas grid parameter, networkingparameter, customer parameter, security parameter, device identificationparameter, or time-stamp parameter.

The first device may also include a processor that is configured tocontrol a message broker and/or message client in the first device. Forexample, the processor may include the functionality/components of theprocessor 150 illustrated in FIG. 1E. Moreover, the message brokerand/or message client may include an embedded protocol that isstandardized with respect to the field message bus 140. In someembodiments, the embedded protocol of the message broker and/or messageclient may be configured to interface with a translator unit that isbetween a device protocol and the field message bus 140. Additionally oralternatively, the embedded protocol of the message broker and/ormessage client may be configured to interface with a plurality of fieldmessage buses.

The first device and/or the field message bus 140 may be spaced apartfrom a data center (e.g., an electric utility data center 130) thatincludes an utility head end system H. Moreover, the field message bus140 may be configured to provide communications independently of a datacenter message bus (e.g., the data center message bus 120) of theutility head end system H.

In some embodiments, a first device indicated with respect to FIGS.11A-11D and 12A-12C may be an electric utility meter, a transformer, alight, an electric grid control device, an electric grid protectiondevice, a line sensor, a weather sensor, an Advanced MeteringInfrastructure (AMI) device, an analog or digital sensor connected to anelectric utility asset, an electric generator, an electric turbine, anelectric boiler, an electric vehicle, an intelligent switching device, ahome appliance, a battery storage device, a capacitor device, a solarpower device, a smart generation device, an emission monitoring device,a water heater, a thermostat, a server, or a voltage regulator.

Referring now to FIG. 13, an illustration is provided of a data modelingand analytics framework, according to various embodiments. For example,FIG. 13 illustrates a security application 1301 that may be uniformacross an entire enterprise. Moreover, FIG. 13 illustrates a commonsemantic model 1302 for the entire enterprise.

Protocols described according to various embodiments herein may bebrokerless or may have a broker. A protocol described herein may providemediation of data, as well as translation and contextualization. Forexample, a protocol described herein may have a physical broker thatmanages data routing and access to the field message bus 140. The brokermay decide when devices/nodes can publish and subscribe todata/messages. As an example, the broker may let messages in and out ata given time interval (e.g., every second).

Alternatively, a protocol described herein may be brokerless (i.e., mayhave no broker at all). A brokerless protocol may be asynchronous andthus may allow devices/nodes to constantly publish and subscribe todata/messages, instead of using a schedule. Accordingly, as a particulardevice/node publishes/subscribes, it can continue to send messages untilthe messages go through, which may improve system reliability,robustness, speed, and scalability.

For example, a brokerless protocol may inherently share data through asemantic model. Specifically, a brokerless protocol may use Quality ofService (QoS) with a defined semantic model to share data. As anexample, a brokerless protocol may use QoS as an input to defineprioritization of traffic (e.g., to define high priority traffic) on amessage bus. In other words, the protocol may use QoS to decide whichtraffic has priority, which may improve reliability of the network. DataDistribution Service (DDS) is one example of a brokerless protocol.Moreover, QoS can be used to manage security. For example, QoS may alignwith cyber-security applications that can use Quality of Trust (QoT) toimpede abnormal or untrusted traffic from publishing or subscribing tothe message bus.

In some embodiments, the devices/nodes described herein may communicateusing both a brokered protocol and a brokerless protocol. For example, aprotocol with a broker can communicate with a protocol that isbrokerless. In some embodiments, the same device/node could use both abroker protocol and a brokerless protocol. Moreover, in someembodiments, different devices within the same network/system couldcommunicate using different ones of a broker protocol and a brokerlessprotocol, respectively.

As an example of using both a brokered protocol and a brokerlessprotocol, a device/node that uses multiple message buses in a system mayrun Message Queuing Telemetry Transport (MQTT), which is a brokerprotocol, whereas a field area network (which shares data seamlesslyacross whole system) in the system may use a brokerless protocol. Inother words, a local area network in the system may be brokered, whereasa field area network in the system may be brokerless. Moreover, multiplebuses may run simultaneously with multiple different protocols that maybe brokered or brokerless.

Regardless of whether a protocol is brokered or brokerless, the protocolmay manage translation, contextualization, and routing via publishingand subscribing to data topics that are defined in a semantic model. Inparticular, a common semantic model 1302 may provide for contextualizingand seamlessly routing the data between publishers and subscribers on amessage bus, thus improving the interchangeability of hardware andsoftware. Moreover, a brokerless protocol may automatically discoverdata topics via the common semantic model 1302.

According to various embodiments, translation and semanticcontextualization may be performed in a field area network, in enddevices, and/or in customer-premise networks (e.g., local area networksof customers), instead of performing all translation and semanticcontextualization between an enterprise application and head-end systemsin a data center. Contextualization may refer to making sense oftranslated data. Moreover, according to various embodiments herein,contextualization refers to contextualizing data before it goes to adata center (e.g., the electric utility data center 130). In otherwords, contextualization may be provided/managed by a protocol outsideof a data center, according to various embodiments herein. For example,a brokerless protocol outside of a data center may provide/manage thecontextualization. Specifically, the protocol may add context to amessage by adding schema such as an Extensible Markup Language (XML)Schema Definition (XSD) file, a Resource Description Framework (RDF)file, or an XML file. In particular, the protocol may add the schema toa virtual embedded environment that is hosting the message bus protocol.

Various embodiments described herein may provide an enterprise-widecybersecurity platform 1301. For example, in some embodiments, asecurity application 1301 may run on top of a message bus API. Moreover,the security application 1301 may sit at multiple tiers of theenterprise rather than only at a data center. The security application1301 may be on a communication node C, a customer device, or any virtualenvironment. In particular, instead of relying on different types ofsecurity in an enterprise, the security application 1301 may be onany/all devices/nodes in the enterprise, thus providing a uniformsecurity application throughout the enterprise.

A semantic model may be a conceptual data model that may be defined by aparticular utility company or by the broader utility industry. Forexample, a semantic model may provide a common definition of howdifferent meters interpret the meaning of data. In other words, asemantic model may provide a common definition of how different metersmeasure voltage and power, and set alarms, among other meter functions.As an example, a semantic model may determine whether the meters measurevoltage with one decimal point or two decimal points, among otherdecisions regarding how the meters interpret the meaning of data.According to various embodiments described herein, a common semanticmodel 1302 may be used as an input to a message bus (e.g., a fieldmessage bus 140).

In particular, the common semantic model 1302 (which may be one level upfrom schema that sits locally on every virtual environment of a fieldarea network) may be provided throughout an entire system/enterprise. Inother words, the common semantic model 1302 may be provided both beforeand after the message bus.

Moreover, the common semantic model 1302 may extensible such that it maybe shared across the entire system/enterprise. In some embodiments, thecommon semantic model 1302 may be dynamically extensible, which meansthat extension of the common semantic 1302 model to a new element/aspectof the system/enterprise should not break the system/enterprise.Furthermore, in some embodiments, the system/enterprise may validate thecommon semantic model 1302 by checking/testing the common semantic model1302 for consistency.

In some embodiments, a field message bus 140 may provide failover,compression, and persistence (e.g., log data for auditing) for dataoutside of a data center. For example, brokerless protocols may beplaced in enterprise areas needing failover. The brokerless protocolsmay provide a distribution of different machines (e.g., devices ornodes) copying the same data. Accordingly, if one machine fails, theothers should still have the data, thus providing redundancy (ofinformation on the field message bus 140) outside of the data center.

In some embodiments, a field message bus 140 may enable remote firmwareupgrades and can provide revision control. In other words, the fieldmessage bus 140 may provide common version control (common revisions)for applications, firmware, etc. Moreover, the common revisions can beperformed remotely and sent to all devices/nodes in an enterprise.

Some embodiments may allow interrogation of other devices to discovercapabilities and to configure the device(s) or database(s) collectingdata. For example, a communications node C adjacent a meter mayinterrogate (i.e., ask) the meter, may discover (e.g., determine whatthe meter is capable of), and then may feed the information to asemantic model, which may then send the information to the entirenetwork such that the entire network sees the capabilities. Moreover,the database may be inside a device such as a meter or a communicationsnode C. Accordingly, interrogation and discovery of diagnostics may beprovided for assets in a customer location (e.g., a home, a commercialbuilding, or an industrial plant), a grid, a substation, and/or a powerplant. Predictive capabilities may be enabled by data that is securelyobtained and understood by a field message bus 140. For example,prediction may include analyzing data to predict capabilities orfailures of a device.

Some embodiments may distribute computing across multiple differentprocessors (and architecture types such as ARM, x86, etc.), memorypartitions (and types such as Flash, RAM, SD, MMC, etc.), multipleoperating systems, multiple virtual machines, and multiple physicalnodes. In other words, computing may be distributed anywhere andeverywhere in a system.

Moreover, some embodiments may allow optimization of processor andmemory capacity/performance on a hosting device or on remote devices.Optimization may provided by sharing resources/capacity among multipledevices. For example, one communications node C can offload storage orprocessing to another communications node C. Accordingly, in addition tothe low processing requirements of various embodiments described herein,resources/capacity of devices/nodes may be optimized/allocated (e.g.,offloaded or split between devices/nodes).

Some embodiments may allow dynamic and adaptive programmability ofAnalog-to-Digital (A/D) converter chips (e.g., Field-Programmable GateArray (FPGA) chips) that are connected to an analog Input/Output (I/O)block of a communications node C. In other words, some embodiments mayuse a message bus protocol to change the behavior of an FPGA (or anyother type of hardware that is convertible/reprogrammable). For example,the message bus protocol can change the instructions of hardware, suchas by telling (e.g., instructing/commanding) hardware that waspreviously functioning as a meter to function as something else.Moreover, such changes/reprogramming may be performed remotely.Accordingly, the message bus protocol can be used to redefine thefunction of hardware. Specifically, a general purpose A/D convertermodule may be provided on a node and may be reprogrammed. A/D capabilitymay thus be provided anywhere in a network and can be accessed remotelyfrom anywhere in the network.

According to various embodiments described herein, a field message bus140 (rather than a head end system H) may obtain data from differentprotocols, and may then provide interoperability using a layer oftranslation (e.g., the common model/ETL mapping illustrated in FIG. 6).Moreover, the field message bus 140 may operate in the field of autility system that includes a gas grid, an electric grid, or a watergrid, and that may further include a telecommunications network,information technology (e.g., analytics, architecture, data management,etc.), sensors on a generator, weather devices, environmental devices,and/or customer devices. Furthermore, it will be understood that theutility system may have a distributed architecture including any number(e.g., 1, 2, 3, 4, or more) of tiers, assets/nodes/devices, applications(synchronous and asynchronous), and message buses, respectively.

In the specification, various embodiments of the present inventiveconcepts have been disclosed and, although specific terms are employed,they are used in a generic and descriptive sense only and not forpurposes of limitation. Those skilled in the art will readily appreciatethat many modifications are possible for the disclosed embodimentswithout materially departing from the teachings and advantages of thepresent inventive concepts. The present inventive concepts are definedby the following claims, with equivalents of the claims to be includedtherein.

1-13. (canceled)
 14. A method of operating a communication node, themethod comprising: using a message broker controlled by a virtualmachine in the communication node to provide a protocol to interfacewith a field message bus comprising a standards-based or open-sourceApplication Programming Interface (API); and transmitting or receivingdata corresponding to an electric grid device, via the field messagebus.
 15. The method of claim 14, wherein: the communication nodecomprises a first communication node; the field message bus interfaceswith a second communication node; and the first and second communicationnodes comprise respective peer communication nodes comprising the fieldmessage bus therebetween.
 16. The method of claim 15, wherein the firstand second communication nodes correspond to different first and secondvendors, respectively.
 17. The method of claim 15, wherein the first andsecond communication nodes correspond to different first and secondhierarchical tiers, respectively, in a hierarchical arrangement ofcommunication nodes.
 18. The method of claim 14, further comprisingusing the protocol of the message broker to interface with a translatorunit that is between a device protocol and the field message bus. 19.The method of claim 14, further comprising using the protocol of themessage broker to interface with a standards-based oropen-source-API-based application in the communication node.
 20. Themethod of claim 14, further comprising using the protocol of the messagebroker to interface with a plurality of field message buses.
 21. Themethod of claim 14, wherein the virtual machine operates using anapplication processor or a partition of a central processing unit of thecommunication node.
 22. The method of claim 14, further comprisingisolating an application processing unit of the communication node froma central processing unit of the communication node, using the virtualmachine.
 23. A computer program product comprising a non-transitorycomputer readable storage medium including computer readable programcode therein configured to perform the method of claim
 14. 24-36.(canceled)
 37. A communication node, comprising: a network interfaceconfigured to provide communications with a first electric grid device;and a processor configured to control a virtual machine in thecommunication node, the virtual machine configured to provide a messagebroker that is configured to interface with a field message bus and/oranother communication node corresponding to a second electric griddevice wherein: the field message bus comprises a standards-based oropen-source Application Programming Interface (API); the message brokeris configured to provide a protocol to interface with the field messagebus comprising the standards-based or open-source API; and the virtualmachine is configured to transmit or receive data corresponding to thesecond electric grid device, via the field message bus.
 38. Thecommunication node of claim 37, wherein: the communication nodecomprises a first communication node; the other communication nodecomprises a second communication node configured to interface with thefield message bus; and the first and second communication nodes compriserespective peer communication nodes comprising the field message bustherebetween.
 39. The communication node of claim 38, wherein the firstand second communication nodes correspond to different first and secondvendors, respectively.
 40. The communication node of claim 38, whereinthe first and second communication nodes correspond to different firstand second hierarchical tiers, respectively, in a hierarchicalarrangement of communication nodes.
 41. The communication node of claim37, wherein the protocol of the message broker is configured tointerface with a translator unit that is between a device protocol andthe field message bus.
 42. The communication node of claim 37, whereinthe protocol of the message broker is configured to interface with astandards-based or open-source-API-based application in thecommunication node.
 43. The communication node of claim 37, wherein theprotocol of the message broker is configured to interface with aplurality of field message buses.
 44. The communication node of claim37, wherein the virtual machine is configured to operate using anapplication processor or a partition of a central processing unit of thecommunication node.
 45. The communication node of claim 37, wherein thevirtual machine is configured to isolate an application processing unitof the communication node from a central processing unit of thecommunication node. 46-84. (canceled)